SGI Enlighten DSM 1.1/SGI EnlightenDSM 1.1.iso/sco5x/admin/help/C/online0504.hlp

Text File | 1998-06-30 | 13KB | 370 lines

    Modify User

    This window is used to modify a user accounts.
    This window contains the following fields:

    Hostnames

    If you want to limit the creation of this account to specific
    hostnames within a pool, enter those hostnames in this field. If you
    are using multiple entries, leave a blank between each entry. You
    can also use the arrow button to the right to select the available
    hosts from the current pool.

    Login name

    The Login name is a unique name which identifies a user account. A
    user needs a login and a password to gain access to the system. The
    login name must be unique and the first character should be set in
    lower case (e.g., cHE034). You may also use macros in this field.
    See "User Account Macros" below for more details.

    Real name

    This is the user's actual name. This field can identify a person,
    company, or organization. You can use this field to associate the
    sometimes cryptic Login name with the actual user's name. On larger
    systems, this name matching is invaluable.

    Office

    This field should contain the location where the user will normally
    access the system. The field can be an office number, an assigned
    location code or a department name. This field does not allow
    punctuation characters.

    Telephone

    This field can contain the telephone number, telephone extension, or
    some other information to help locate and contact the user. The
    format of the field is user definable.

    At this point you can have Enlighten automatically fill in the
    remainder of the form by clicking on the Add button. The default
    values entered depend on the values set in Configure --> New User
    Templates window.

    Otherwise, you should fill-in the rest of the fields yourself. The
    fields and their defaults are:

    User ID

    This field contains the UID number. The UNIX operating system uses
    this number to identify each user. This number does not have to be
    unique, but should be for easier system administration. Enter the
    UserID number to be assigned to this user account.

    If the New User Template you're using is set to automatically
    generate a unique UID, then this field will be initialized with that
    number.

    Note: If this field is left blank, Enlighten will prompt you for an
    entry in this field when it tries to create the user.

    Home dir.

    The Home dir. field specifies where the user's start-up directory is
    attached. Most systems will use /usr or /home as the default parent
    directory. Each user will have their own directory created under the
    default home directory, e.g. /usr/charlie. Enlighten stores /usr as
    the default HOME directory unless you change this field.

    If you specify a HOME directory which does not exists, Enlighten
    creates and initializes it. Enlighten initializes the HOME directory
    by executing the HOME directory initialization script
    $ENLIGHTEN/scripts/user.rc. This copies the initialization files
    (e.g., .profile and .cshrc) into the HOME directory. You can modify
    this script to perform other initialization procedures.

    You may also use macros in this field. See "User Account Macros" below
    for more details.

    Shell

    The Shell is a program that acts as a translator between the user
    and the UNIX operating system. There may be several standard shells
    on a system, including the C Shell, the Bourne Shell, the Korn Shell
    and the restricted Bourne, C and Korn Shells. This, however, does
    not stop experienced users from creating custom shells. Each shell
    has its own start-up executable program as shown on the following
    page.

        Bourne Shell /bin/sh

        Restricted Bourne Shell /bin/rsh

        C Shell /bin/csh

        Korn Shell /bin/ksh

        Restricted Korn Shell /bin/rksh

        Other user defined

    Enlighten uses the Bourne shell as the default shell in this field
    (/bin/sh). All users on the system do not have to use the same
    shell; this is a matter of user preference, as each shell offers
    different functionality. The number of standard shells available for
    this field depends on your system. Click on the arrow button to
    display a pick list of available shells.

    Group name

    Every user account must be assigned to at least one User Group. The
    User Group is part of the UNIX security system; each user group has
    specific read, write, and execute privileges associated with every
    file created on the system.

    Enter the primary Group name for this user or leave this field blank
    to have the default assigned. Click on the arrow button for a pick
    list of defined User Groups. If you enter a Group Name which does
    not exist, Enlighten will prompt for a correct Group Name when it
    tries to create the user.

    Add Groups

    You can use this field to put the user in additional user groups.
    This will effectively give the user more group privileges beyond
    those set in the primary user group. Enter the names of the user
    groups to which the user should also belong. Click on the arrow
    button for a pick list of defined User Groups. Select the User
    Groups and click on the Apply button to import them.

    Password

    The password is part of the UNIX security system. Each user must
    have a password. If you make the password the same as the user
    login, the user can then reset the password to one of his or her own
    choice. Don't use passwords such as spouse names, pet names, or
    addresses, they are easy for another user to guess. You may also use
    macros in this field. See "User Account Macros" below for more
    details.

    Note: If the entry in the password field is not long enough, an
    error message will be displayed when you try to add this user
    account.

    Expires

    For systems that support password aging, this optional field
    contains the time when the password will expire. Once a password has
    expired, the system will force the user to change their password the
    next time they login to the system.

    If this field is left blank, the appropriate default parameter will
    be used. If no default is set in the User Add window (when you're
    adding a user), password aging will be turned off for that user.

    To specify a time format, see "TIME FORMATS" below.

    Span

    In conjunction with the Expires field, this field defines the
    minimum period of time which needs to elapse before the user can
    change his or her password. You can, however, change the user's
    password at any time by using the Password button in the User
    Configuration window.
    To specify a time format, see "TIME FORMATS" below.

    Last Login

    This field specifies the date and time the user last logged on.

    Pwd change

    This field specifies when the user last changed passwords.


    Buttons

    This window contains the following buttons.

    Modify

    Once you've entered the relevant information, click on the Modify
    button to modify the user. If the information is incorrect use the
    mouse to navigate through the fields and make the necessary changes.
    When complete, click on the modify button again.

    Next

    You can use the Next button to modify additional user accounts if
    you've selected more than one account to modify from the User
    Configuration list.

    Clear Fields

    Click on this button to clear the existing choices in all fields.

    Close

    Click on this button to discard any changes and close the window.


    USER ACCOUNT MACROS

    You can use macros to help initialize the form fields when you
    create a User Account. You can enter these macros manually. Or you
    can have them fill (some of) the form fields automatically by first
    defining them in a New User Template and using that template when
    you create the user account.

    The following types of fields accept macros in these two windows:

    + Login Name
    + Home dir.
    + Password
    + Mail Alias

    For working examples, see "Macro Name" on page J-3.

    Format

    A macro has the following format:

        %<Modifiers><Macro Name>

    Modifiers

    <Modifiers> are optional (you can define them multiple times). You
    can use the <Modifiers> to specify only specific parts of the field,
    such as the first letter of the field, or to manipulate and convert
    the given input.

    A modifier has the following format:


    [<Converter><Range>]

    where <Converter> is one or more of the following characters:

        l - Convert the resulting string to lower case
        L - Same as `l'
        u - Convert the resulting string to upper case
        U - Same as `u'
        s - Do not include SPACEs
        S - Same as `s'
        _ - Replace SPACEs with underscores (_)

    and the <Range> applies to the complete string in the field (by
    default). Or you can apply a range to a specific word in the input
    string.

    Consequently, a <Range> has the following format:

        $<word number><Character Range>

    where <word number> shows the word's sequence in the string (this is
    optional). The first word would be addressed as $1, the second word
    as $2, and so on. You can also use $0 to address the first word.

    <Character Range> is a comma separated list of character ranges in
    the form. If you specify a <word number>, you must first use a comma
    (`,') in the range list.

    The character range itself has the following format:

        <start char>-<end char>

    where <start char> and <end char> are character numbers. You can
    omit one end of the range to signify the "start of string" and "end
    of string" respectively. Ranges which go beyond the end of the
    string are truncated to match the string.

    Macro Name

    <Macro Name> is one of the following characters:

        g - replace with the users' GID
        u - replace with the users' UID
        G - replace with the users' group name
        U - replace with the users' login name (username)
        R - replace with data from the users' Real Name field
        O - replace with date from the users' Office field
        T - replace with date from the users' Telephone field

    Examples

    These definitions make more sense when they are viewed as examples.
    Assume for the following example, the following data is true:

        Real Name: Thomas Kraus
        Login Name: tmk
        UID: 302

    You could then define the following macros and see the following
    substitutions.

        Field Name   Macro               Value
        -------------------------------------------
        Home Dir     /home/%U           /home/tmk
        Password     %U-%u              tmk-302
        Mail Alias   %[u$1]R_%[u$2]R    THOMAS_KRAUS
        Login Name   %[l$1,1][l$2,-6]   tkraus

    Some explanations:

    /home/%U Create the directory /home/<login name>

    %U-%u Get the User name and add the UID (separated by a dash)

    %[u$1]R_%[u$2]R Get the first word of the users' real name and add
    the second word of the user's real name (separated by an
    underscore). Convert both strings to upper case.

    %[l$1,1][l$3,-6]R Take the first letter of the users first name and
    the first six letters of the users' last name. Convert both strings
    to lower case.


    TIME FORMATS

    There are several fields throughout the Enlighten product where you
    can specify a date/time format. For each of these fields, you can
    specify the date and/or time period in two ways: absolutely or
    relatively.

    The first is as a static period, where the period entered is the
    absolute period used in the search. This is the only way to search
    for a combined date/time format. To look for a file created since
    May 10, 1996 at 12 noon, you could use the entry: May 10 96 at
    12:00.

    The second is a relative period, where the period entered is set
    against the current system clock time and then applied during the
    search. This is strictly a time OR date format, e.g., 2 seconds or 1
    month. To find users who have been logged in during the last three
    days, you could use the entry: 3 days.

    Either way, the format is case-insensitive. For example, you could
    use JAN, Jan, or jan as the abbreviation for the month of January.
    This appendix shows all the BNF time measurements in initial caps
    (e.g., Jan or January, 2 Sec or 2 Seconds, etc.).

    Some typical uses of the static format in a Date search field are:

    Absolute: 15 1996 (defaults to the current month)

        Jan 1 97
        July 4 (defaults to the current year)

    Some additional uses of the absolute format in a Time search field
    are:

        June 15 at 3 PM (defaults to the current year)
        June 16 at 2AM (defaults to the current year)
        June 17 96 at 15:31
        18 at 9:31:14 AM (defaults to current month AND year)

    Some typical uses of the relative format in a Date search field are:

        Relative: 1 second

        5 Min
        1 day
        2 weeks
        1 Year

    The rest of this appendix defines the time formats you can use
    whenever you fill in a date and/or time field.